This repository was archived by the owner on May 15, 2024. It is now read-only.
Allows running stand-alone (WIP) #10
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE
This small change allows running
cargo-openstandalone as well as as a subcommand ofcargo...well, almost.Running
cargo open <crate>works as expected. Runningcargo-open <crate>also works...but not quite as expected. The problem is$CARGO_HOMEisn't set whencargodoesn't run. (Also note,cargo-openorcargo openwithout a crate still spits out the required error messages 😉)If you know of a way to cleanly set
$CARGO_HOME(to include when users are usingmultirust) it should be as simple as setting that variable. I'm just not familiar enough withcargo(yet) to set it manually.Overall this would make hacking on
cargo-opena little easier/faster. So if it's something you'd like to pursue I'll keep looking for something that'll work 😄